home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: news.uwa.edu.au!DIALix!wmcpet!news
- From: mario@wmcmis.DIALix.oz.au (Mario Degasperi (Programmer - MIS))
- Subject: MS Visual C DLL File problems
- Message-ID: <Dnvqu5.KqK@wmcpet.dialix.oz.au>
- Keywords: DLL, Visual C
- Sender: news@wmcpet.dialix.oz.au
- Reply-To: mario@wmcmis.DIALix.oz.au
- Organization: WMC - IT Services
- Date: Thu, 7 Mar 1996 04:22:52 GMT
-
-
-
- Can any body help
-
- Using Microsoft Visual C (Version 5.1), it seems that if a
- function from one DLL (DLL A) calls a function in a different
- DLL (DLL B), passing to it a file pointer, the characteristics
- and state of the file are changed in DLL B (eg, the file position
- pointer and the file contents) almost as if the file pointer
- is no longer valid or pointing to a different space in memory.
-
- The result is that when a read is attempted, it returns EOF
- or reads garbage.
-
- The file is opened in DLL A using fopen for read only. There
- is nothing wrong with the code itself since it works on other
- platforms using normal 'C' objects linked in to an executable.
- It also works if the offending function in DLL B is moved to
- DLL A.
-
- If anybody has encounter this problem or similar problems, or
- knows a solution, could you please let me know.
-
- Thanks, Mario.
- --
-
- +=======================================================================+
- | --- Mario Degasperi - Programmer |
- |/* *\ Contracting to Western Mining Corporation ACN 004 184 598 |
- || ? | |
- ||\_/| Phone : (09) 4422136 |
- |\___/ MIS: mario@wmcmis.dialix.oz.au
- +=======================================================================+
-
-
-